In-manifest update event

ABSTRACT

There is included a method and apparatus comprising computer code configured to cause a processor or processors to perform publishing media presentation description data comprising main live program data, and signaling a client device about ad data and in-manifest data where the ad data instructs the client device of an initial end time at which to end a display of an ad by switching a display at the client device from the ad to the main live program data and where the in-manifest data instructs the client device to determine, during a streaming of the ad to the client device, an updated end time, prior to the end time, at which to end the streaming of the ad by switching the streaming at the client device from the ad to the main live program data.

CROSS REFERENCE TO RELATED APPLICATION

The present application claims priority to provisional application U.S.No. 62/897,228 filed on Sep. 6, 2019 which is hereby expresslyincorporated by reference, in its entirety, into the presentapplication.

BACKGROUND 1. Field

The present disclosure is directed to an in-manifest update eventsignaling a streaming client that a manifest update is necessary.

2. Description of Related Art

In Dynamic Adaptive Streaming over HTTP (DASH), such as MPEG-DASH, aninband media presentation description (MPD) validity expiration eventmay be used to signal clients a need for updating a manifest. However,technical disadvantageous are experienced as an inband even is tied tomedia segments such that such events can only be received from a serverproviding the content, and therefore, when a client is streaming contentfrom a separate server (e.g., an advertisement (ad) server), the mainserver cannot add the inband events to the media segments originatingfrom the separate server.

During a live streaming of the content, there are certain moments thatthe ad can be inserted (e.g., at an ad-break). A nominal duration of adsis decided by the content server and is inserted into the manifest.During that period, the client goes to the ad-server and streams and/orplays back the ad. Such technical disadvantages noted above compoundedwhen, for example during the live content event, the ad-server mustprovide the ad content for that exact duration that is indicated in theoriginal manifest, and in real cases, the live server may want to earlyterminate the ads, because the event is back from a break, and theclient needs to stop streaming the ads and switch back to the livecontent. However, since the inband MPD validity expiration event isincluded with the media segments, and since the client is not streamingthe content from the live server, at least during the ad period, even ifthe live server inserts the MPD validity events, the client will notreceive that update for at least the above reasons.

Therefore, there is a desire for a technical solution to such problems.

SUMMARY

The proposed method and apparatus herein may be used separately orcombined in any order. Further, each of the features, encoder, anddecoder may be implemented by processing circuitry (e.g., one or moreprocessors or one or more integrated circuits). In one example, the oneor more processors executes a program that is stored in a non-transitorycomputer-readable medium.

This disclosure introduces, among other things, an in-manifest event,which is inserted in an MPD, equivalent of an inband MPD validityexpiration event. This in-manifest event may have the same properties ofan inband MPD validity expiration event, and therefore the DASH clientcan process the in-manifest event in a way. There is also disclosedherein how the in-manifest event can be used for early termination ofany of pre-roll and mid-roll ads.

There is included a method and apparatus comprising memory configured tostore computer program code and a processor or processors configured toaccess the computer program code and operate as instructed by thecomputer program code. The compute program code includes publishing codeconfigured to cause the at least one processor to publish mediapresentation description (MPD) data comprising main live program dataand signaling code configured to cause the at least one processor tosignal a client device about ad data and in-manifest data, where the addata instructs the client device of an initial end time at which to enda display of an ad by switching a display at the client device from thead to the main live program data, and where the in-manifest datainstructs the client device to determine, during a streaming of the adto the client device, an updated end time, prior to the end time, atwhich to end the streaming of the ad by switching the streaming at theclient device from the ad to the main live program data.

According to exemplary embodiments, signaling the client device aboutthe ad data and the in-manifest data comprises instructing the clientdevice to stream the ad as a mid-roll ad in between segments ofstreaming of the main live program data.

According to exemplary embodiments, signaling the client device aboutthe ad data and the in-manifest data further comprises instructing theclient device to switch from an origin server, providing the main liveprogram data, to an ad server separate from the origin server and toobtain the mid-roll ad from the ad server.

According to exemplary embodiments, the in-manifest data comprisesinstructions that the client device is to determine the updated end timeby accessing a remote element, during streaming of the mid-roll ad bythe client device, and determining whether the remote element indicatesthe updated end time.

According to exemplary embodiments, the in-manifest data comprisesfurther instructions that the client device is to access the remoteelement at a predetermined frequency prior to the end time.

According to exemplary embodiments, the instructions of the in-manifestdata instruct the client device to access the remote element via xlinkdata.

According to exemplary embodiments, signaling the client device aboutthe ad data and the in-manifest data comprises instructing the clientdevice to stream the ad as a pre-roll ad prior to streaming of the mainlive program data.

According to exemplary embodiments, the in-manifest data comprisesinstructions that the client device is to determine the updated end timeby accessing a remote element, during streaming of the pre-roll ad bythe client device, and determining whether the remote element indicatesthe updated end time.

According to exemplary embodiments, the in-manifest data comprisesfurther instructions that the client device is to access the remoteelement at a predetermined frequency prior to the end time.

BRIEF DESCRIPTION OF THE DRAWINGS

Further features, nature, and various advantages of the disclosedsubject matter will be more apparent from the following detaileddescription and the accompanying drawings in which:

FIGS. 1-5 are schematic illustrations of diagrams in accordance withembodiments.

FIGS. 6 and 7 are simplified flow diagrams in accordance withembodiments.

FIG. 8 is a schematic illustration of a diagram in accordance withembodiments.

DETAILED DESCRIPTION

The proposed features discussed below may be used separately or combinedin any order. Further, the embodiments may be implemented by processingcircuitry (e.g., one or more processors or one or more integratedcircuits). In one example, the one or more processors execute a programthat is stored in a non-transitory computer-readable medium.

FIG. 1 illustrates a simplified block diagram of a communication system100 according to an embodiment of the present disclosure. Thecommunication system 100 may include at least two terminals 102 and 103interconnected via a network 105. For unidirectional transmission ofdata, a first terminal 103 may code video data at a local location fortransmission to the other terminal 102 via the network 105. The secondterminal 102 may receive the coded video data of the other terminal fromthe network 105, decode the coded data and display the recovered videodata. Unidirectional data transmission may be common in media servingapplications and the like.

FIG. 1 illustrates a second pair of terminals 101 and 104 provided tosupport bidirectional transmission of coded video that may occur, forexample, during videoconferencing. For bidirectional transmission ofdata, each terminal 101 and 104 may code video data captured at a locallocation for transmission to the other terminal via the network 105.Each terminal 101 and 104 also may receive the coded video datatransmitted by the other terminal, may decode the coded data and maydisplay the recovered video data at a local display device.

In FIG. 1, the terminals 101, 102, 103 and 104 may be illustrated asservers, personal computers and smart phones but the principles of thepresent disclosure are not so limited. Embodiments of the presentdisclosure find application with laptop computers, tablet computers,media players and/or dedicated video conferencing equipment. The network105 represents any number of networks that convey coded video data amongthe terminals 101, 102, 103 and 104, including for example wirelineand/or wireless communication networks. The communication network 105may exchange data in circuit-switched and/or packet-switched channels.Representative networks include telecommunications networks, local areanetworks, wide area networks and/or the Internet. For the purposes ofthe present discussion, the architecture and topology of the network 105may be immaterial to the operation of the present disclosure unlessexplained herein below.

FIG. 2 illustrates, as an example for an application for the disclosedsubject matter, the placement of a video encoder and decoder in astreaming environment. The disclosed subject matter can be equallyapplicable to other video enabled applications, including, for example,video conferencing, digital TV, storing of compressed video on digitalmedia including CD, DVD, memory stick and the like, and so on.

A streaming system may include a capture subsystem 203, that can includea video source 201, for example a digital camera, creating, for example,an uncompressed video sample stream 213. That sample stream 213 may beemphasized as a high data volume when compared to encoded videobitstreams and can be processed by an encoder 202 coupled to the camera201. The encoder 202 can include hardware, software, or a combinationthereof to enable or implement aspects of the disclosed subject matteras described in more detail below. The encoded video bitstream 204,which may be emphasized as a lower data volume when compared to thesample stream, can be stored on a streaming server 205 for future use.One or more streaming clients 212 and 207 can access the streamingserver 205 to retrieve copies 208 and 206 of the encoded video bitstream204. A client 212 can include a video decoder 211 which decodes theincoming copy of the encoded video bitstream 208 and creates an outgoingvideo sample stream 210 that can be rendered on a display 209 or otherrendering device (not depicted). In some streaming systems, the videobitstreams 204, 206 and 208 can be encoded according to certain videocoding/compression standards. Examples of those standards are notedabove and described further herein.

FIG. 3 may be a functional block diagram of a video decoder 300according to an embodiment of the present invention.

A receiver 302 may receive one or more codec video sequences to bedecoded by the decoder 300; in the same or another embodiment, one codedvideo sequence at a time, where the decoding of each coded videosequence is independent from other coded video sequences. The codedvideo sequence may be received from a channel 301, which may be ahardware/software link to a storage device which stores the encodedvideo data. The receiver 302 may receive the encoded video data withother data, for example, coded audio data and/or ancillary data streams,that may be forwarded to their respective using entities (not depicted).The receiver 302 may separate the coded video sequence from the otherdata. To combat network jitter, a buffer memory 303 may be coupled inbetween receiver 302 and entropy decoder/parser 304 (“parser”henceforth). When receiver 302 is receiving data from a store/forwarddevice of sufficient bandwidth and controllability, or from anisosychronous network, the buffer 303 may not be needed, or can besmall. For use on best effort packet networks such as the Internet, thebuffer 303 may be required, can be comparatively large and canadvantageously of adaptive size.

The video decoder 300 may include a parser 304 to reconstruct symbols313 from the entropy coded video sequence. Categories of those symbolsinclude information used to manage operation of the decoder 300, andpotentially information to control a rendering device such as a display312 that is not an integral part of the decoder but can be coupled toit. The control information for the rendering device(s) may be in theform of Supplementary Enhancement Information (SEI messages) or VideoUsability Information parameter set fragments (not depicted). The parser304 may parse/entropy-decode the coded video sequence received. Thecoding of the coded video sequence can be in accordance with a videocoding technology or standard, and can follow principles well known to aperson skilled in the art, including variable length coding, Huffmancoding, arithmetic coding with or without context sensitivity, and soforth. The parser 304 may extract from the coded video sequence, a setof subgroup parameters for at least one of the subgroups of pixels inthe video decoder, based upon at least one parameters corresponding tothe group. Subgroups can include Groups of Pictures (GOPs), pictures,tiles, slices, macroblocks, Coding Units (CUs), blocks, Transform Units(TUs), Prediction Units (PUs) and so forth. The entropy decoder/parsermay also extract from the coded video sequence information such astransform coefficients, quantizer parameter values, motion vectors, andso forth.

The parser 304 may perform entropy decoding/parsing operation on thevideo sequence received from the buffer 303, so to create symbols 313.The parser 304 may receive encoded data, and selectively decodeparticular symbols 313. Further, the parser 304 may determine whetherthe particular symbols 313 are to be provided to a Motion CompensationPrediction unit 306, a scaler/inverse transform unit 305, an IntraPrediction Unit 307, or a loop filter 311.

Reconstruction of the symbols 313 can involve multiple different unitsdepending on the type of the coded video picture or parts thereof (suchas: inter and intra picture, inter and intra block), and other factors.Which units are involved, and how, can be controlled by the subgroupcontrol information that was parsed from the coded video sequence by theparser 304. The flow of such subgroup control information between theparser 304 and the multiple units below is not depicted for clarity.

Beyond the functional blocks already mentioned, decoder 300 can beconceptually subdivided into a number of functional units as describedbelow. In a practical implementation operating under commercialconstraints, many of these units interact closely with each other andcan, at least partly, be integrated into each other. However, for thepurpose of describing the disclosed subject matter, the conceptualsubdivision into the functional units below is appropriate.

A first unit is the scaler/inverse transform unit 305. Thescaler/inverse transform unit 305 receives quantized transformcoefficient as well as control information, including which transform touse, block size, quantization factor, quantization scaling matrices,etc. as symbol(s) 313 from the parser 304. It can output blockscomprising sample values, that can be input into aggregator 310.

In some cases, the output samples of the scaler/inverse transform 305can pertain to an intra coded block; that is: a block that is not usingpredictive information from previously reconstructed pictures, but canuse predictive information from previously reconstructed parts of thecurrent picture. Such predictive information can be provided by an intrapicture prediction unit 307. In some cases, the intra picture predictionunit 307 generates a block of the same size and shape of the block underreconstruction, using surrounding already reconstructed informationfetched from the current (partly reconstructed) picture 309. Theaggregator 310, in some cases, adds, on a per sample basis, theprediction information the intra prediction unit 307 has generated tothe output sample information as provided by the scaler/inversetransform unit 305.

In other cases, the output samples of the scaler/inverse transform unit305 can pertain to an inter coded, and potentially motion compensatedblock. In such a case, a Motion Compensation Prediction unit 306 canaccess reference picture memory 308 to fetch samples used forprediction. After motion compensating the fetched samples in accordancewith the symbols 313 pertaining to the block, these samples can be addedby the aggregator 310 to the output of the scaler/inverse transform unit(in this case called the residual samples or residual signal) so togenerate output sample information. The addresses within the referencepicture memory form where the motion compensation unit fetchesprediction samples can be controlled by motion vectors, available to themotion compensation unit in the form of symbols 313 that can have, forexample X, Y, and reference picture components. Motion compensation alsocan include interpolation of sample values as fetched from the referencepicture memory when sub-sample exact motion vectors are in use, motionvector prediction mechanisms, and so forth.

The output samples of the aggregator 310 can be subject to various loopfiltering techniques in the loop filter unit 311. Video compressiontechnologies can include in-loop filter technologies that are controlledby parameters included in the coded video bitstream and made availableto the loop filter unit 311 as symbols 313 from the parser 304, but canalso be responsive to meta-information obtained during the decoding ofprevious (in decoding order) parts of the coded picture or coded videosequence, as well as responsive to previously reconstructed andloop-filtered sample values.

The output of the loop filter unit 311 can be a sample stream that canbe output to the render device 312 as well as stored in the referencepicture memory 557 for use in future inter-picture prediction.

Certain coded pictures, once fully reconstructed, can be used asreference pictures for future prediction. Once a coded picture is fullyreconstructed and the coded picture has been identified as a referencepicture (by, for example, parser 304), the current reference picture 309can become part of the reference picture buffer 308, and a fresh currentpicture memory can be reallocated before commencing the reconstructionof the following coded picture.

The video decoder 300 may perform decoding operations according to apredetermined video compression technology that may be documented in astandard, such as ITU-T Rec. H.265. The coded video sequence may conformto a syntax specified by the video compression technology or standardbeing used, in the sense that it adheres to the syntax of the videocompression technology or standard, as specified in the videocompression technology document or standard and specifically in theprofiles document therein. Also necessary for compliance can be that thecomplexity of the coded video sequence is within bounds as defined bythe level of the video compression technology or standard. In somecases, levels restrict the maximum picture size, maximum frame rate,maximum reconstruction sample rate (measured in, for example megasamplesper second), maximum reference picture size, and so on. Limits set bylevels can, in some cases, be further restricted through HypotheticalReference Decoder (HRD) specifications and metadata for HRD buffermanagement signaled in the coded video sequence.

In an embodiment, the receiver 302 may receive additional (redundant)data with the encoded video. The additional data may be included as partof the coded video sequence(s). The additional data may be used by thevideo decoder 300 to properly decode the data and/or to more accuratelyreconstruct the original video data. Additional data can be in the formof, for example, temporal, spatial, or signal-to-noise ratio (SNR)enhancement layers, redundant slices, redundant pictures, forward errorcorrection codes, and so on.

FIG. 4 may be a functional block diagram of a video encoder 400according to an embodiment of the present disclosure.

The encoder 400 may receive video samples from a video source 401 (thatis not part of the encoder) that may capture video image(s) to be codedby the encoder 400.

The video source 401 may provide the source video sequence to be codedby the encoder (303) in the form of a digital video sample stream thatcan be of any suitable bit depth (for example: 8 bit, 10 bit, 12 bit, .. . ), any colorspace (for example, BT.601 Y CrCB, RGB, . . . ) and anysuitable sampling structure (for example Y CrCb 4:2:0, Y CrCb 4:4:4). Ina media serving system, the video source 401 may be a storage devicestoring previously prepared video. In a videoconferencing system, thevideo source 401 may be a camera that captures local image informationas a video sequence. Video data may be provided as a plurality ofindividual pictures that impart motion when viewed in sequence. Thepictures themselves may be organized as a spatial array of pixels,wherein each pixel can comprise one or more samples depending on thesampling structure, color space, etc. in use. A person skilled in theart can readily understand the relationship between pixels and samples.The description below focuses on samples.

According to an embodiment, the encoder 400 may code and compress thepictures of the source video sequence into a coded video sequence 410 inreal time or under any other time constraints as required by theapplication. Enforcing appropriate coding speed is one function ofController 402. Controller controls other functional units as describedbelow and is functionally coupled to these units. The coupling is notdepicted for clarity. Parameters set by controller can include ratecontrol related parameters (picture skip, quantizer, lambda value ofrate-distortion optimization techniques, . . . ), picture size, group ofpictures (GOP) layout, maximum motion vector search range, and so forth.A person skilled in the art can readily identify other functions ofcontroller 402 as they may pertain to video encoder 400 optimized for acertain system design.

Some video encoders operate in what a person skilled in the art readilyrecognizes as a “coding loop.” As an oversimplified description, acoding loop can consist of the encoding part of an encoder 402 (“sourcecoder” henceforth) (responsible for creating symbols based on an inputpicture to be coded, and a reference picture(s)), and a (local) decoder406 embedded in the encoder 400 that reconstructs the symbols to createthe sample data that a (remote) decoder also would create (as anycompression between symbols and coded video bitstream is lossless in thevideo compression technologies considered in the disclosed subjectmatter). That reconstructed sample stream is input to the referencepicture memory 405. As the decoding of a symbol stream leads tobit-exact results independent of decoder location (local or remote), thereference picture buffer content is also bit exact between local encoderand remote encoder. In other words, the prediction part of an encoder“sees” as reference picture samples exactly the same sample values as adecoder would “see” when using prediction during decoding. Thisfundamental principle of reference picture synchronicity (and resultingdrift, if synchronicity cannot be maintained, for example because ofchannel errors) is well known to a person skilled in the art.

The operation of the “local” decoder 406 can be the same as of a“remote” decoder 300, which has already been described in detail abovein conjunction with FIG. 3. Briefly referring also to FIG. 4, however,as symbols are available and en/decoding of symbols to a coded videosequence by entropy coder 408 and parser 304 can be lossless, theentropy decoding parts of decoder 300, including channel 301, receiver302, buffer 303, and parser 304 may not be fully implemented in localdecoder 406.

An observation that can be made at this point is that any decodertechnology except the parsing/entropy decoding that is present in adecoder also necessarily needs to be present, in substantially identicalfunctional form, in a corresponding encoder. The description of encodertechnologies can be abbreviated as they are the inverse of thecomprehensively described decoder technologies. Only in certain areas amore detail description is required and provided below.

As part of its operation, the source coder 403 may perform motioncompensated predictive coding, which codes an input frame predictivelywith reference to one or more previously-coded frames from the videosequence that were designated as “reference frames.” In this manner, thecoding engine 407 codes differences between pixel blocks of an inputframe and pixel blocks of reference frame(s) that may be selected asprediction reference(s) to the input frame.

The local video decoder 406 may decode coded video data of frames thatmay be designated as reference frames, based on symbols created by thesource coder 403. Operations of the coding engine 407 may advantageouslybe lossy processes. When the coded video data may be decoded at a videodecoder (not shown in FIG. 4), the reconstructed video sequencetypically may be a replica of the source video sequence with someerrors. The local video decoder 406 replicates decoding processes thatmay be performed by the video decoder on reference frames and may causereconstructed reference frames to be stored in the reference picturecache 405. In this manner, the encoder 400 may store copies ofreconstructed reference frames locally that have common content as thereconstructed reference frames that will be obtained by a far-end videodecoder (absent transmission errors).

The predictor 404 may perform prediction searches for the coding engine407. That is, for a new frame to be coded, the predictor 404 may searchthe reference picture memory 405 for sample data (as candidate referencepixel blocks) or certain metadata such as reference picture motionvectors, block shapes, and so on, that may serve as an appropriateprediction reference for the new pictures. The predictor 404 may operateon a sample block-by-pixel block basis to find appropriate predictionreferences. In some cases, as determined by search results obtained bythe predictor 404, an input picture may have prediction references drawnfrom multiple reference pictures stored in the reference picture memory405.

The controller 402 may manage coding operations of the video coder 403,including, for example, setting of parameters and subgroup parametersused for encoding the video data.

Output of all aforementioned functional units may be subjected toentropy coding in the entropy coder 408. The entropy coder translatesthe symbols as generated by the various functional units into a codedvideo sequence, by loss-less compressing the symbols according totechnologies known to a person skilled in the art as, for exampleHuffman coding, variable length coding, arithmetic coding, and so forth.

The transmitter 409 may buffer the coded video sequence(s) as created bythe entropy coder 408 to prepare it for transmission via a communicationchannel 411, which may be a hardware/software link to a storage devicewhich would store the encoded video data. The transmitter 409 may mergecoded video data from the video coder 403 with other data to betransmitted, for example, coded audio data and/or ancillary data streams(sources not shown).

The controller 402 may manage operation of the encoder 400. Duringcoding, the controller 405 may assign to each coded picture a certaincoded picture type, which may affect the coding techniques that may beapplied to the respective picture. For example, pictures often may beassigned as one of the following frame types:

An Intra Picture (I picture) may be one that may be coded and decodedwithout using any other frame in the sequence as a source of prediction.Some video codecs allow for different types of Intra pictures,including, for example Independent Decoder Refresh Pictures. A personskilled in the art is aware of those variants of I pictures and theirrespective applications and features.

A Predictive picture (P picture) may be one that may be coded anddecoded using intra prediction or inter prediction using at most onemotion vector and reference index to predict the sample values of eachblock.

A Bi-directionally Predictive Picture (B Picture) may be one that may becoded and decoded using intra prediction or inter prediction using atmost two motion vectors and reference indices to predict the samplevalues of each block. Similarly, multiple-predictive pictures can usemore than two reference pictures and associated metadata for thereconstruction of a single block.

Source pictures commonly may be subdivided spatially into a plurality ofsample blocks (for example, blocks of 4×4, 8×8, 4×8, or 16×16 sampleseach) and coded on a block-by-block basis. Blocks may be codedpredictively with reference to other (already coded) blocks asdetermined by the coding assignment applied to the blocks' respectivepictures. For example, blocks of I pictures may be codednon-predictively or they may be coded predictively with reference toalready coded blocks of the same picture (spatial prediction or intraprediction). Pixel blocks of P pictures may be coded non-predictively,via spatial prediction or via temporal prediction with reference to onepreviously coded reference pictures. Blocks of B pictures may be codednon-predictively, via spatial prediction or via temporal prediction withreference to one or two previously coded reference pictures.

The video coder 400 may perform coding operations according to apredetermined video coding technology or standard, such as ITU-T Rec.H.265. In its operation, the video coder 400 may perform variouscompression operations, including predictive coding operations thatexploit temporal and spatial redundancies in the input video sequence.The coded video data, therefore, may conform to a syntax specified bythe video coding technology or standard being used.

In an embodiment, the transmitter 409 may transmit additional data withthe encoded video. The source coder 403 may include such data as part ofthe coded video sequence. Additional data may comprisetemporal/spatial/SNR enhancement layers, other forms of redundant datasuch as redundant pictures and slices, Supplementary EnhancementInformation (SEI) messages, Visual Usability Information (VUI) parameterset fragments, and so on.

FIG. 5 is a schematic illustrations of a general workflow 500 includinginterfaces IF1 and IF2 between an origin server 501, a client 502, andan ad server 503 respectively. Such general and simplified architectureillustration corresponds to embodiments described herein includingsignaling configurations including an in-manifest update eventovercoming the technical disadvantageous discussed above, and of course,the interfaces IF1 and IF2 need not be direct connections but insteadmay be merely simplifications of one or more networked connectionsbetween those illustrated element representations.

FIG. 6 is a simplified flow diagram 600 regarding various embodimentsincluding one or more mid-roll ads with technically advantageous earlytermination via at least features regarding the herein disclosedin-manifest features.

At S60, it is determined to proceed to S61 at which an origin server,such as origin server 501 in FIG. 5, publishes an MPD containing aprogram, such as a main live program which may be occurring in or nearreal-time for example. At S62, it is considered whether an ad-breakoccurs, and if so, when it is determined that an ad-break has occurred,via mid-roll signaling such as with MPEG-DASH for example, the originserver inserts at least an in-manifest/inband MPD validity expirationevent (herein also referred to simply as an “event”) to signal a needfor an MPD update at S63, and at S64, when the client receives suchevent, the client parses the event, and, based on timing information inthat event, such as one or more timers representing an initial ad-breakduration and a time or frequency at which to check for updates describedfurther below, calculates an expiration time in a timeline on which toupdate or check for an update to MPD data.

Accordingly, additionally at S64, when the time or frequency or signalotherwise occurs according to the event, the client requests an MPDupdate, from the origin server or otherwise from a resource describedbelow and indicated by the event, before the MPD expiration time for theoverall ad-break as initially reported to the client, and in response,the client receives such update, if any, and updates the clientsexpected MPD information as illustrated at S65. Such S63-S65 featuresmay occur prior to or after at least partial playing of the ad, such asvia the client switching from the origin server to the ad server, suchas ad-server 503 as illustrated simply in FIG. 5.

At S65, the client switches to the ad-break and starts streaming fromthe ad-server. The new MPD herein contains an in-manifest MPD validityexpiration event stream which has a remote element using xlink, and thenew MPD also has one or more of a minimumUpdatePeriod value either forthat event stream or as inherited from an MPD@minimumUpdatePeriod valuedescribed further herein below. At S67, while streaming content from thead-server, the client request MPD validity expiration EventStream, witha frequency equal to or larger than a minimumUpdatePeriod, from at leastthe resource noted above and as defined, for example, by xlink. Wheneverthe client receives a new MPD validity expiration Event from thatEventStream, such as at S68, the client parses that new event andprocesses that event according to the timing model of MPD validityexpiration, and the client updates the MPD before expiration time set bythe MPD validity expiration, such as the otherwise end of the ad-break(termination) previously indicated. The update may signal an end of thead-break and a switch back, as at S69, to the stream (e.g., live stream)via the client switching back from the ad server to the origin server ormay signal one or more new parameters of the event. That is, at S69, thenew MPD update may be determined to include an updated ad durationinstructing the client to switch back to the live server at either a newearly terminating moment in the timeline or immediately as an earlyterminating moment with respect to such one or more mid-roll of a singleor sequence of mid-roll ads.

FIG. 7 is a simplified flow diagram 700 regarding various embodimentsincluding one or more pre-roll ads with technically advantageous earlytermination via at least features regarding the herein disclosedin-manifest features.

At S71, an origin server, such as origin server 501 in FIG. 5, publishesan MPD containing a pre-roll ad and a program, such as a main liveprogram which may be occurring in or near real-time for example. At S72,the client starts streaming the pre-roll ad from the ad-server.According to exemplary embodiments, the MPD contains an in manifest MPDvalidity expiration event stream which has a remove element using xlink,such as similarly described above with respect to FIG. 6, and the newMPD also has one or more of a minimumUpdatePeriod value either for thatevent stream or as inherited from an MPD@minimumUpdatePeriod valuedescribed further herein below. At S77, while streaming content from thead-server, the client request MPD validity expiration EventStream, witha frequency equal to or larger than a minimumUpdatePeriod, from at leastthe resource noted above and as defined, for example, by xlink. Wheneverthe client receives a new MPD validity expiration Event from thatEventStream, such as at S78, the client parses that new event andprocesses that event according to the timing model of MPD validityexpiration, and the client updates the MPD before expiration time set bythe MPD validity expiration, such as the otherwise end of the ad-break(termination) previously indicated. The update may signal an end of thead-break and a switch, as at S79, to the stream (e.g., live stream) viathe client switching back from the ad server to the origin server or maysignal one or more new parameters of the event. That is, at 79, the newMPD update may be determined to include an updated ad durationinstructing the client to switch to the live server at either a newearly terminating moment in the timeline or immediately as an earlyterminating moment with respect to such one or more pre-roll of a singleor sequence of pre-roll ads. The illustration at FIG. 7 with respect tothe end at S79 will be understood to also link to S60 of FIG. 6 at whichfurther possible content delivery with respect to also one or moremid-roll ads may proceed as described above, such as with FIG. 6. Thatis, the features of FIG. 7, may immediately precede those of FIG. 7.

According to exemplary embodiments, such signaling may be defined, forexample with an in-manifest MPD validity expiration, as follows. Thereis herein defined a scheme included a specific schemeIDUri that may bedefined for an in-manifest MPD validity expiration such as:“urn:mpeg::dash:manifest-event:2020”, and an EventStream elementcarrying such events may use such URI in their @schemeIDUri.

Further with respect to such signaling, as similar to Inband MPDvalidity expiration events, same values may be used to signal a type ofMPD update event as:

TABLE 1 @value Description 1 Event@messageData contains the smallestpublish time for valid MPDs. Event@presentationTime defines the offsetfrom which only MPDs with publish times equal or larger than the abovepublish time are valid. The Event@duration expresses the remainingduration of Media Presentation from the event time. If the eventduration is 0, Media Presentation ends at the event time. If 0xFFFF, themedia presentation duration may be unknown. In a case in which both apresentation_time_delta and an event)duration are zero, then a MediaPresentation may be ended. 2 indicates that MPD validity expirationevents as with the @value = 1 noted above. In addition to suchindication, the message includes an MPD Patch as defined in subclause5.10.4.3 in DASHEvent.mpd field within the message_data field. 3indicates that MPD validity expiration events as @value = 1 as notedabove. In addition to such indication, the message includes a completeMPD Patch as defined in subclause 5.10.4.4 in DASHEvent.mpd field withinthe message_data field.

Further, events with same id values may be considered equivalent, andtherefore, receipt of a plurality of such events may result in checkingwhether a value is a same and then processing only one as adequate, suchas per check or per some time period predetermined with respect to theevent and/or client.

Further, there may be use of in-manifest MPD expiration events with MPDlevel EventStreams, and in order to completely untie the in-manifest MPDexpiration events from periods, these events can be used forEventStreams that are defined at an MPD level and are independent to oneor more periods according to exemplary embodiments.

Accordingly, by exemplary embodiments described herein, the technicalproblems noted above may be advantageously improved upon by one or moreof these technical solutions as This disclosure introduces, among otherthings, an in-manifest event, which is inserted in an MPD, equivalent ofan inband MPD validity expiration event. This in-manifest event may havethe same properties of an inband MPD validity expiration event, andtherefore the DASH client can process the in-manifest event in a way.There is also disclosed herein how the in-manifest event can be used forearly termination of any of pre-roll and mid-roll ads which has anadvantageous technical effect in solution to the technical problemsdescribed above regarding technical absence of desireable earlytermination of such ads.

The techniques described above, can be implemented as computer softwareusing computer-readable instructions and physically stored in one ormore computer-readable media or by a specifically configured one or morehardware processors. For example, FIG. 8 shows a computer system 800suitable for implementing certain embodiments of the disclosed subjectmatter.

The computer software can be coded using any suitable machine code orcomputer language, that may be subject to assembly, compilation,linking, or like mechanisms to create code comprising instructions thatcan be executed directly, or through interpretation, micro-codeexecution, and the like, by computer central processing units (CPUs),Graphics Processing Units (GPUs), and the like.

The instructions can be executed on various types of computers orcomponents thereof, including, for example, personal computers, tabletcomputers, servers, smartphones, gaming devices, internet of thingsdevices, and the like.

The components shown in FIG. 8 for computer system 800 are exemplary innature and are not intended to suggest any limitation as to the scope ofuse or functionality of the computer software implementing embodimentsof the present disclosure. Neither should the configuration ofcomponents be interpreted as having any dependency or requirementrelating to any one or combination of components illustrated in theexemplary embodiment of a computer system 800.

Computer system 800 may include certain human interface input devices.Such a human interface input device may be responsive to input by one ormore human users through, for example, tactile input (such as:keystrokes, swipes, data glove movements), audio input (such as: voice,clapping), visual input (such as: gestures), olfactory input (notdepicted). The human interface devices can also be used to capturecertain media not necessarily directly related to conscious input by ahuman, such as audio (such as: speech, music, ambient sound), images(such as: scanned images, photographic images obtain from a still imagecamera), video (such as two-dimensional video, three-dimensional videoincluding stereoscopic video).

Input human interface devices may include one or more of (only one ofeach depicted): keyboard 801, mouse 802, trackpad 803, touch screen 810,joystick 805, microphone 806, scanner 808, camera 807.

Computer system 800 may also include certain human interface outputdevices. Such human interface output devices may be stimulating thesenses of one or more human users through, for example, tactile output,sound, light, and smell/taste. Such human interface output devices mayinclude tactile output devices (for example tactile feedback by thetouch-screen 810, or joystick 805, but there can also be tactilefeedback devices that do not serve as input devices), audio outputdevices (such as: speakers 809, headphones (not depicted)), visualoutput devices (such as screens 810 to include CRT screens, LCD screens,plasma screens, OLED screens, each with or without touch-screen inputcapability, each with or without tactile feedback capability—some ofwhich may be capable to output two dimensional visual output or morethan three dimensional output through means such as stereographicoutput; virtual-reality glasses (not depicted), holographic displays andsmoke tanks (not depicted)), and printers (not depicted).

Computer system 800 can also include human accessible storage devicesand their associated media such as optical media including CD/DVD ROM/RW820 with CD/DVD 811 or the like media, thumb-drive 822, removable harddrive or solid state drive 823, legacy magnetic media such as tape andfloppy disc (not depicted), specialized ROM/ASIC/PLD based devices suchas security dongles (not depicted), and the like.

Those skilled in the art should also understand that term “computerreadable media” as used in connection with the presently disclosedsubject matter does not encompass transmission media, carrier waves, orother transitory signals.

Computer system 800 can also include interface 899 to one or morecommunication networks 898. Networks 898 can for example be wireless,wireline, optical. Networks 898 can further be local, wide-area,metropolitan, vehicular and industrial, real-time, delay-tolerant, andso on. Examples of networks 898 include local area networks such asEthernet, wireless LANs, cellular networks to include GSM, 3G, 4G, 5G,LTE and the like, TV wireline or wireless wide area digital networks toinclude cable TV, satellite TV, and terrestrial broadcast TV, vehicularand industrial to include CANBus, and so forth. Certain networks 898commonly require external network interface adapters that attached tocertain general-purpose data ports or peripheral buses (850 and 851)(such as, for example USB ports of the computer system 800; others arecommonly integrated into the core of the computer system 800 byattachment to a system bus as described below (for example Ethernetinterface into a PC computer system or cellular network interface into asmartphone computer system). Using any of these networks 898, computersystem 800 can communicate with other entities. Such communication canbe uni-directional, receive only (for example, broadcast TV),uni-directional send-only (for example CANbusto certain CANbus devices),or bi-directional, for example to other computer systems using local orwide area digital networks. Certain protocols and protocol stacks can beused on each of those networks and network interfaces as describedabove.

Aforementioned human interface devices, human-accessible storagedevices, and network interfaces can be attached to a core 840 of thecomputer system 800.

The core 840 can include one or more Central Processing Units (CPU) 841,Graphics Processing Units (GPU) 842, a graphics adapter 817, specializedprogrammable processing units in the form of Field Programmable GateAreas (FPGA) 843, hardware accelerators for certain tasks 844, and soforth. These devices, along with Read-only memory (ROM) 845,Random-access memory 846, internal mass storage such as internalnon-user accessible hard drives, SSDs, and the like 847, may beconnected through a system bus 848. In some computer systems, the systembus 848 can be accessible in the form of one or more physical plugs toenable extensions by additional CPUs, GPU, and the like. The peripheraldevices can be attached either directly to the core's system bus 848, orthrough a peripheral bus 851. Architectures for a peripheral bus includePCI, USB, and the like.

CPUs 841, GPUs 842, FPGAs 843, and accelerators 844 can execute certaininstructions that, in combination, can make up the aforementionedcomputer code. That computer code can be stored in ROM 845 or RAM 846.Transitional data can be also be stored in RAM 846, whereas permanentdata can be stored for example, in the internal mass storage 847. Faststorage and retrieval to any of the memory devices can be enabledthrough the use of cache memory, that can be closely associated with oneor more CPU 841, GPU 842, mass storage 847, ROM 845, RAM 846, and thelike.

The computer readable media can have computer code thereon forperforming various computer-implemented operations. The media andcomputer code can be those specially designed and constructed for thepurposes of the present disclosure, or they can be of the kind wellknown and available to those having skill in the computer software arts.

As an example and not by way of limitation, the computer system havingarchitecture 1200, and specifically the core 840 can providefunctionality as a result of processor(s) (including CPUs, GPUs, FPGA,accelerators, and the like) executing software embodied in one or moretangible, computer-readable media. Such computer-readable media can bemedia associated with user-accessible mass storage as introduced above,as well as certain storage of the core 840 that are of non-transitorynature, such as core-internal mass storage 847 or ROM 845. The softwareimplementing various embodiments of the present disclosure can be storedin such devices and executed by core 840. A computer-readable medium caninclude one or more memory devices or chips, according to particularneeds. The software can cause the core 840 and specifically theprocessors therein (including CPU, GPU, FPGA, and the like) to executeparticular processes or particular parts of particular processesdescribed herein, including defining data structures stored in RAM 846and modifying such data structures according to the processes defined bythe software. In addition or as an alternative, the computer system canprovide functionality as a result of logic hardwired or otherwiseembodied in a circuit (for example: accelerator 844), which can operatein place of or together with software to execute particular processes orparticular parts of particular processes described herein. Reference tosoftware can encompass logic, and vice versa, where appropriate.Reference to a computer-readable media can encompass a circuit (such asan integrated circuit (IC)) storing software for execution, a circuitembodying logic for execution, or both, where appropriate. The presentdisclosure encompasses any suitable combination of hardware andsoftware.

While this disclosure has described several exemplary embodiments, thereare alterations, permutations, and various substitute equivalents, whichfall within the scope of the disclosure. It will thus be appreciatedthat those skilled in the art will be able to devise numerous systemsand methods which, although not explicitly shown or described herein,embody the principles of the disclosure and are thus within the spiritand scope thereof

What is claimed is:
 1. A method for video signaling performed by atleast one processor, the method comprising: publishing mediapresentation description (MPD) data comprising main live program data;and signaling a client device about ad data and in-manifest data,wherein the ad data instructs the client device of an initial end timeat which to end a display of an ad by switching a display at the clientdevice from the ad to the main live program data, and wherein thein-manifest data instructs the client device to determine, during astreaming of the ad to the client device, an updated end time, prior tothe end time, at which to end the streaming of the ad by switching thestreaming at the client device from the ad to the main live programdata.
 2. The method according to claim 1, wherein signaling the clientdevice about the ad data and the in-manifest data comprises instructingthe client device to stream the ad as a mid-roll ad in between segmentsof streaming of the main live program data.
 3. The method according toclaim 2, wherein signaling the client device about the ad data and thein-manifest data further comprises instructing the client device toswitch from an origin server, providing the main live program data, toan ad server separate from the origin server and to obtain the mid-rollad from the ad server.
 4. The method according to claim 3, wherein thein-manifest data comprises instructions that the client device is todetermine the updated end time by accessing a remote element, duringstreaming of the mid-roll ad by the client device, and determiningwhether the remote element indicates the updated end time.
 5. The methodaccording to claim 4, wherein the in-manifest data comprises furtherinstructions that the client device is to access the remote element at apredetermined frequency prior to the end time.
 6. The method accordingto claim 4, wherein the instructions of the in-manifest data instructthe client device to access the remote element via xlink data.
 7. Themethod according to claim 1, wherein signaling the client device aboutthe ad data and the in-manifest data comprises instructing the clientdevice to stream the ad as a pre-roll ad prior to streaming of the mainlive program data.
 8. The method according to claim 7, wherein thein-manifest data comprises instructions that the client device is todetermine the updated end time by accessing a remote element, duringstreaming of the pre-roll ad by the client device, and determiningwhether the remote element indicates the updated end time.
 9. The methodaccording to claim 8, wherein the in-manifest data comprises furtherinstructions that the client device is to access the remote element at apredetermined frequency prior to the end time.
 10. The method accordingto claim 9, wherein the instructions of the in-manifest data instructthe client device to access the remote element via xlink data.
 11. Anapparatus for video signaling, the apparatus comprising: at least onememory configured to store computer program code; at least one processorconfigured to access the computer program code and operate as instructedby the computer program code, the computer program code including:publishing code configured to cause the at least one processor topublish media presentation description (MPD) data comprising main liveprogram data; and signaling code configured to cause the at least oneprocessor to signal a client device about ad data and in-manifest data,wherein the ad data instructs the client device of an initial end timeat which to end a display of an ad by switching a display at the clientdevice from the ad to the main live program data, and wherein thein-manifest data instructs the client device to determine, during astreaming of the ad to the client device, an updated end time, prior tothe end time, at which to end the streaming of the ad by switching thestreaming at the client device from the ad to the main live programdata.
 12. The apparatus according to claim 11, wherein signaling theclient device about the ad data and the in-manifest data comprisesinstructing the client device to stream the ad as a mid-roll ad inbetween segments of streaming of the main live program data.
 13. Theapparatus according to claim 12, wherein signaling the client deviceabout the ad data and the in-manifest data further comprises instructingthe client device to switch from an origin server, providing the mainlive program data, to an ad server separate from the origin server andto obtain the mid-roll ad from the ad server.
 14. The apparatusaccording to claim 13, wherein the in-manifest data comprisesinstructions that the client device is to determine the updated end timeby accessing a remote element, during streaming of the mid-roll ad bythe client device, and determining whether the remote element indicatesthe updated end time.
 15. The apparatus according to claim 14, whereinthe in-manifest data comprises further instructions that the clientdevice is to access the remote element at a predetermined frequencyprior to the end time.
 16. The apparatus according to claim 14, whereinthe instructions of the in-manifest data instruct the client device toaccess the remote element via xlink data.
 17. The apparatus according toclaim 11, wherein signaling the client device about the ad data and thein-manifest data comprises instructing the client device to stream thead as a pre-roll ad prior to streaming of the main live program data.18. The apparatus according to claim 17, wherein the in-manifest datacomprises instructions that the client device is to determine theupdated end time by accessing a remote element, during streaming of thepre-roll ad by the client device, and determining whether the remoteelement indicates the updated end time.
 19. The apparatus according toclaim 18, wherein the in-manifest data comprises further instructionsthat the client device is to access the remote element at apredetermined frequency prior to the end time.
 20. A non-transitorycomputer readable medium storing a program configured to cause acomputer to: publish media presentation description (MPD) datacomprising main live program data; and signal a client device about addata and in-manifest data, wherein the ad data instructs the clientdevice of an initial end time at which to end a display of an ad byswitching a display at the client device from the ad to the main liveprogram data, and wherein the in-manifest data instructs the clientdevice to determine, during a streaming of the ad to the client device,an updated end time, prior to the end time, at which to end thestreaming of the ad by switching the streaming at the client device fromthe ad to the main live program data.